GitHub header

All Systems Operational

About This Site

For the status of GitHub Enterprise Cloud - EU, please visit: eu.githubstatus.com
For the status of GitHub Enterprise Cloud - Australia, please visit: au.githubstatus.com
For the status of GitHub Enterprise Cloud - US, please visit: us.githubstatus.com

Git Operations ? Operational
Webhooks ? Operational
Visit www.githubstatus.com for more information Operational
API Requests ? Operational
Issues ? Operational
Pull Requests ? Operational
Actions ? Operational
Packages ? Operational
Pages ? Operational
Codespaces ? Operational
Copilot Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Sep 11, 2025

No incidents reported today.

Sep 10, 2025
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Sep 10, 14:02 UTC
Update - Actions hosted runners are taking longer to come online, leading to high wait times or job failures.
Sep 10, 13:31 UTC
Investigating - We are investigating reports of degraded performance for Actions
Sep 10, 13:23 UTC
Sep 9, 2025

No incidents reported.

Sep 8, 2025

No incidents reported.

Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

Sep 4, 2025
Resolved - On September 4, 2025 between 15:30 UTC and 20:00 UTC the REST API endpoints git/refs, git/refs/*, and git/matching-refs/* were degraded and returned elevated errors for repositories with reference counts over 22k. On average, the request error rate to these specific endpoints was 0.5%. Overall REST API availability remained 99.9999%. This was due to the introduction of a code change that added latency to reference evaluations and overly affected repositories with many branches, tags, or other references.

We mitigated the incident by reverting the new code.

We are working to improve performance testing and to reduce our time to detection and mitigation of issues like this one in the future.

Sep 4, 20:25 UTC
Update - The deployment has completed and we expect customers who have been impacted to see recovery. We are continuing to monitor.
Sep 4, 20:05 UTC
Update - We are in the process of deploying the PR to revert the change that was causing timeouts to this endpoint. We will update again once that deployment is complete.
Sep 4, 19:28 UTC
Update - We have identified a deployed change that correlates with the increase in 5XX errors to the GitRefs REST API. This is particularly affecting requests for repos with very large numbers of commits. We are working on rolling back this change which we expect will resolve the issue.
Sep 4, 18:57 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate.
Sep 4, 18:52 UTC
Update - Customers are experiencing 504 responses for some API requests for regarding repo refs/tags. We are investigating.
Sep 4, 18:18 UTC
Investigating - We are currently investigating this issue.
Sep 4, 18:16 UTC
Sep 3, 2025

No incidents reported.

Sep 2, 2025
Resolved - Between August 21, 2025 at 15:00 UTC, and September 2, 2025 at 15:22 UTC the avatars.githubusercontent.com image service was degraded and failed to display user avatars for users in the Middle East. During this time, avatar images appeared broken on github.com for affected users. On average, this impacted about 82% of users routed through one of our Middle East-based points-of-presence, which represents about 0.14% of global users.

This was due to a configuration change within GitHub's edge infrastructure in the affected region, causing HTTP requests to fail. As a result, image requests returned HTTP 503 errors. The failure to detect the issues was the result of an alerting threshold set too low.

We mitigated the incident by removing the affected site from service, which restored avatar serving for impacted users.

To prevent this from recurring, we have tuned configuration defaults for graceful degradation. We also added new health checks to automatically shift traffic from impacted sites. We are updating our monitoring to prevent undetected errors like this in the future.

Sep 2, 15:44 UTC
Investigating - We are currently investigating this issue.
Sep 2, 15:17 UTC
Sep 1, 2025

No incidents reported.

Aug 31, 2025

No incidents reported.

Aug 30, 2025

No incidents reported.

Aug 29, 2025

No incidents reported.

Aug 28, 2025

No incidents reported.